Add Range

The purpose of Open Shortest Path First Protocol (OSPF) is to provide routing information between routers.

OSPF is a link state protocol because routers in an OSPF network make routing decisions based upon a complete topological database for the routing domain built from information flooded throughout the routing domain.

Use Add Range to add more information to already existing OSPF information. With it you can add ranges to areas as well as neighbors to non-broadcast networks. OSPF areas can be defined in terms of address ranges. External to the area, a single route is advertised for each address range. For example, if an OSPF area were to consist of all subnets of the class B network 128.185.0.0, it would be defined as consisting of a single address range. The address range would be specified as an address of 128.185.0.0 together with a mask of 255.255.0.0. Outside of the area, the entire subnetted network would be advertised as a single route to network 128.185.0.0.

Ranges can be defined to control which routes are advertised externally to an area. There are two choices:

Ranges cannot be used for areas that serve as transit areas for virtual links. Also, when ranges are defined for an area, OSPF will not function correctly if the area is partitioned but is connected by the backbone.

  1. Enter the area number.

  2. Enter the IP address.

    Valid Values: any valid IP address.

    Default Value: none

  3. Enter the IP address mask.

    Valid Values: any valid IP address mask.

    Default Value: none

Select the Submit button.


Add Neighbor

Two routers that have interfaces to a common network are said to be neighbors. Neighbor routers are discovered by the OSPF Hello protocol. Not all neighbor routers become adjacent routers that will exchange link state information. Neighbors on point-to-point links do so, but on multi-access networks, adjacencies are formed only between individual routers and the designated and backup designated routers. These routers are elected automatically for each network once neighbor routers have been discovered by the Hello protocol. The designated router performs two key roles for a network:

Use Add Neighbor to configure neighbors adjacent to the router over this interface. In non-broadcast multi-access networks, neighbors need to be configured to communicate only with those routers that are eligible to become the designated router. In point-to-multipoint networks, at least one end of every logical connection must have a configured neighbor.

  1. Enter the Interface IP address.

    Valid Values: any valid IP address. The last octet must be a zero.

    Default Value: none

  2. Enter the IP Address of Neighbor.

    Valid Values: any valid IP address.

    Default Value: none

  3. Answer the question, Can that router become designated router on this area?.

Select the Submit button.


Delete Range

Use Delete Range to delete ranges of OPSF areas from the current OPSF configuration.

  1. Enter the area number of the range to be deleted.

    Valid Values:

    Default Value: none

  2. Enter the IP Address of Neighbor.

    Valid Values: any valid IP address. The last octet must be a zero.

    Default Value: none

  3. Enter the IP Address Mask of Neighbor.

    Valid Values: any valid IP address mask.

    Default Value: none

Select the Submit button.


Delete Area

Use Delete Area to delete OPSF areas from the current OPSF configuration.

Enter the area number to be deleted.

Select the Submit button.


Delete Interface

Use Delete Interface to delete an interface from the current OPSF configuration.

Enter the interface IP address to be deleted.

Valid Values: any valid IP address.

Default Value: none

Select the Submit button.


Delete Neighbor

Use Delete Neighbor to delete configured neighbors from the current OPSF configuration.

  1. Enter the interface IP address

    Valid Values: any valid IP address.

    Default Value: none

  2. Enter the neighbor IP address to be deleted.

    Valid Values: any valid IP address.

    Default Value: none

Select the Submit button.


Delete Non-Broadcast Descriptor

If the router is connected to a non-broadcast, multi-access network, such as an X.25 PDN, enabling this parameter helps the router discover its OSPF neighbors.

Use Delete Non-Broadcast Descriptor to delete non-broadcast network information from the current OPSF configuration.

Enter the interface IP address.

Valid Values: any valid IP address

Default Value: none

Select the Submit button.


Delete Virtual Link

A virtual link is a type of point-to-point interface that connects two area border routers that are separated by a non-backbone, non-stub area. Because area border routers are part of the OSPF backbone, the virtual link connects the backbone.

Virtual links are considered to be separate router interfaces connecting to the backbone area.

Use Delete Virtual Link to delete a virtual link that you may have set using the Set Virtual-Link option.

  1. Enter the virtual endpoint (router ID) that defines the id of the virtual neighbor.

    Valid Values: any valid IP address

    Default Value: none

  2. Enter the link's transit area.

    Valid Values: any valid IP address

    Default Value: 0.0.0.0

Select the Submit button.


Disable Subnet Advertisement Option

Use this option to discontinue advertisement of a point-to-point interface as a subnet.

Enter the interface IP address.

Valid Values: any valid IP address

Default Value: none

Select the Submit button.


Enable AS Boundary Routing

This option enables the AS boundary routing capability, which allows this router to import routes learned from other protocols (RIP, static, and direct routes) into the OSPF domain.

You must enable this parameter even if the only route you want to import is the default route (destination 0.0.0.0).

All routes are imported with their cost equal to their routing table cost. They are all imported as either Type 1 or Type 2 External Routes, depending on the Routing Protocol Comparison. The metric type used when importing routes determines how the imported cost is viewed by the OSPF domain. When comparing two type 2 metrics, only the external cost is considered in picking the best route. When comparing two type 1 metrics, the external and internal costs of the route are combined before making the comparison. Use Enable AS Boundary Routing to enable the AS boundary routing capability which allows you to import routes learned from other protocols (BGP, RIP, and statically configured information) into the OSPF domain.

  1. Indicate whether you want to import BGP routes.

  2. Select the Submit button.

  3. Indicate whether you want to Automatically generate tags.

  4. Select the Submit button.

  5. Indicate whether you want to Import RIP routes.

    This option specifies that routes learned by RIP will be imported into the OSPF routing domain. Only routes that appear in the RIP input exchange tables will be imported.

    All routes are imported with their cost equal to their routing table cost. They are all imported as either type 1 or 2 external routes, depending on the Routing Protocol Comparison.

  6. Indicate whether you want to Import static routes.

    This option specifies that static routes will be imported into the OSPF routing domain.

    All routes are imported with their cost equal to their routing table cost. They are all imported as either type 1 or 2 external routes, depending on the Routing Protocol Comparison.

  7. Indicate whether you want to Import direct routes.

    This option specifies that direct routes will be imported into the OSPF routing domain.

    All routes are imported with their cost equal to their routing table cost. They are all imported as either type 1 or type 2 external routes, depending on the Routing Protocol Comparison.

  8. Indicate whether you want to Import subnet routes.

    Independent of the external routes (RIP, Static, and Direct routes) you may choose to import, you can also configure whether or not to import subnet routes into the OSPF domain. This option specifies whether or not the router will import subnet routes into the OSPF routing domain.

  9. Indicate whether you want to originate default route.

    This option allows RIP to advertise the router as a default router (called "originating the default route"). The default router performs routing for other routers on an internet that have packets for an unknown network destination.

  10. Select the Submit button.

  11. Select the type of boundary routing: type 1 or type 2.

  12. Enter a Default route cost.

    This parameter specifies the cost that OSPF associates with the default route to its area border router. The cost is used to determine the shortest path for the default route to its area border router.

    Valid Values: 0 to 16777215

    Default Value: 1

  13. Enter a Default forwarding address.

    This parameter specifies the forwarding address that will be used in the imported default route.

    Valid Values: a valid IP address

    Default Value: none

  14. Select the Submit button.

Enable Multicast Forwarding

Use Enable Multicast Forwarding to enable the forwarding of IP multicast (Class D) datagrams. When enabling multicast routing, you are also prompted whether you want to forward IP multicast datagrams between OSPF areas. To run MOSPF (OSPF with multicast extensions), a router currently running OSPF needs only to use this command. You do not need to reenter its configuration information.

Indicate whether you want inter-area multicasting enabled.

Select the Submit button.


Enable OSPF Routing Protocol

The purpose of Open Shortest Path First Protocol (OSPF) is to provide routing information between routers.

OSPF is a link state protocol because routers in an OSPF network make routing decisions based upon a complete topological database for the routing domain built from information flooded throughout the routing domain.

Use Enable OSPF Routing Protocol to enable the entire OSPF protocol. When enabling the OSPF routing protocol, Enter the following two values that will be used to estimate the size of the OSPF link state database:

  1. Total number of AS external routes that will be imported into the OSPF routing domain. A single destination may lead to multiple external routes when it is imported by separate AS boundary routers. For example, if the OSPF routing domain has two AS boundary routers, both importing routes to the same 100 destinations, the number of AS external routes should be set to 200. The router cannot accept more than the configured number of AS external routes. This parameter should be configured identically in all of your OSPF routers.

    Valid Values: 0 to 65535

    Default Value: 100

  2. Total number of OSPF routers in the routing domain.

    This parameter specifies the total number of OSPF routers in the routing domain. This parameter should be configured identically in all of your OSPF routers.

    Valid Values: 0 to 65535

    Default Value: 50

Select the Submit button.


Enable Subnet Advertising Option

For an interface to a point-to-point serial line, use this option to enable the advertisement of a stub route to the subnet that represents the serial line rather than the host route for the other router's address. Enter this router's address for the interface to identify it.

Enter the interface IP address.

Valid Values: any valid IP address

Default Value: none

Select the Submit button.


Join

IP multicasting allows you to address a set of IP hosts using a specific unique IP address. This set is called a group.

Being a member of a group means that you want to receive datagrams sent to the group address. You may send datagrams to a multicast without being a member of a group.

OSPF IP supports both local delivery and forwarding of packets addressed to multicast IP addresses.

Use Join to configure the server as a member of a multicast group. When the server is the member of a multicast group, it responds to PINGS and SNMP queries sent to the group address.

Enter the group address.

This parameter specifies the 6-byte (12-digit hexadecimal) group/multicast address.

Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'

Default Value: none

Select the Submit button.


Leave

Use Leave to remove a server's membership from a multicast group. This will prevent the server from responding to PINGS and SNMP queries sent to the group address.

Enter the address to be deleted.

Valid Values: any valid IP address

Default Value: none

Select the Submit button.


Set Area

Use Set Area to sets the parameters for an OSPF area. If no areas are defined, the server software assumes that all the server's directly attached networks belong to the backbone area (area ID 0.0.0.0).

  1. Enter the area number.

  2. Select the Submit button.

  3. Enter an authentication type.

    This option defines the password used for this OSPF area. When password authentication is used, only packets with the correct authentication key are accepted.

    All OSPF routers attached to the same subnet must have the same Authentication Key. For example, suppose the address mask for this network interface is 255.255.255.0, the IP address is 128.185.138.19 and the authentication key is xyz123. According to the subnet mask and IP address combination, the interface attaches to the subnet 128.185.138.0 of network 128.185.0.0. All other OSPF routers attached to subnet 128.185.138.0 must have their authentication key set to xyz123.

    Valid Values: any 8 characters

    Default Value: 0

  4. Indicate if this is a stub area.

    An area can be a transit area or a stub area (also known as a nontransit area).

Select the Submit button.


Set Comparison

Use Set Comparison to tell the server where the BGP/RIP/static routes fit in the OSPF hierarchy.

This parameter specifies the OSPF external type (1 or 2) assigned to the routes imported into the OSPF routing domain. The type tells the router where the external routes fit in the OSPF routing hierarchy.

OSPF Routing Hierarchy

OSPF has a 4-level routing hierarchy.

The two lower levels consist of the OSPF internal routes (intra-area and inter-area routes). OSPF internal routes take precedence over information obtained from any other sources. To put the external routes on the same level as OSPF External Type 1 routes, use type 1. To put the external routes on the same level as OSPF External Type 2 routes, use type 2.

For example, suppose the type is set to 2 for imported RIP routes. In this case, when RIP routes are imported into the OSPF domain, they will be imported as type 2 externals. All OSPF external type 1 routes override external type 2 routes, regardless of metric. However, if the RIP routes have a smaller cost than the other external type 2 routes, the RIP routes will override the other OSPF external type 2 routes. The type values for all of your OSPF routers must match. If the type values set for the routers are inconsistent, your routing will not function properly.

The metric type used in importing routes determines how the imported cost is viewed by the OSPF domain. When comparing two type 2 metrics, only the external cost is considered in picking the best route. When comparing two type 1 metrics, the external and internal costs of the route are combined before making the comparison.

Choose if you want the comparison to OSPF ASE type 1 or OSPF ADE type 2 external routes.

Select the Submit button.